Open topic with navigation

Managing your Tasks

The tasks are activities that are performed by the TMS users. The tasks are always assigned to users.

The different types of human tasks condition the workflow behavior in different ways.

Human task

Human task has a blue icon. The person accepts or rejects the ownership of the task. On acceptance, the task moves to the In Work view, from which the user can interact with the file (check-out and check-in) and complete the task.

Approval task

Approval task has a yellow icon. The user conditions the flow by accepting or rejecting the task. By accepting the task the user triggers the workflow to continue. By rejecting the task she triggers the workflow to cancel the current level.

• If the task is at Job level, it cancels the rest of the activities in the Job flow.
• If the task is at Language level, it cancels the rest of the activities for the language level.
• If the task is at File level, it cancels the rest of the activities for the file in the current language.

Human Decision task

Human Decision task has a green icon. This type of task is similar to the Human task, except that the user has to select a condition (mark as Passed or Failed) before completing the task.

As for the approval task, the condition determines how the flow will be executed (whether a set of activities is skipped or not). For example a Review task can determine if a Rework task should be executed (when the reviewer sets the Review as "Failed") or not (when the reviewer sets the Review as "Accepted").

New tasks assigned messages on the Home tab

When you log into the Lionbridge TMS™, you can see information about the number of new tasks displayed by project under the My tasks heading in the Home tab Projects view.

To open the project and view the tasks, you can click the green New tasks heading or the blue Tasks In Work heading in the Projects view list. The Project tab is displayed, and depending on which heading you clicked, the Tasks | New or the Tasks | In Work view is displayed on the view pane.

To view the details of the Job contact user, click the Job contact details at the end of the job heading row.

Click Details on a package or a file line to open (and close) an additional pane with detailed information on the package or the file.

You can open (and close) an additional inline pane with detailed TM analysis word count results by clicking the concise wordcount information on the task.

The additional information pane displays the total effort of the file word count in detail. Opening any of the other additional panes closes the currently open pane.

Contacting TMS Support

There is a Contact Support option in the context menu in the Tasks|New and the Tasks|InWorkviews for all assigned tasks (Human, Human Review, CTE Human and CTE Human Review).

When you select the option, the Contact Support dialog is displayed.

You can select the message recipient. Service Desk is available in the list, set as the default value.

Task assignee can input text to describe the problem encountered in their own words inside the 3000 characters limit.

You can click Submit to send the email message.

When you send an email from the Contact Support dialog in TMS, the task details are retrieved (if present) and included in the message, such as:

• TMS User ID, CTE collection ID and the language pair (if the task is a CTE task)
• Step details: Project ID, Step ID, TMS job ID

An email message draft is created with the following header fields included:

• The Subject field with information like other system generated emails, such as
  [Project name] - [Job name] - [Activity name]: A support request was raised.
• The Body field contains the following information:
  • Prefix line identifying that this is an automatically generated message from TMS
  • Problem description entered by user in the Contact dialog
  • Task details
• The To field is filled with the recipient email address from the Contact dialog
• The CC field is filled with the email address of the currently logged-in user
• The From field is filled with the email of the currently logged-in user so that:
  • If the recipient is the Service Desk, the created ticket has this information (Affected user field if internal user or Alternate contact method otherwise) and any notifications in the ticket are sent to the affected user, not to TMS
  • If the recipient is other, the receiver can reply to the email and have the currently logged-in user set in To field in their email client
• The Sender field, acting on behalf of, set to Lionbridge TMS <noreply.tms@lionbridge.com>

The message is sent to the recipient set in the To field.

Related Topics